Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 094b5c180a62fc889233b0a3ee8dbf22f1ab3b27cdcb5a62b190521be0f29f3e

Tx prefix hash: 448650de6777463f73f110a12feb9e84a3baa00b56e919145459663ff5add0e9
Tx public key: f38063b95265eaac34d4a83111a4650c4922d203c2e2b8d48cd18b86d14b3611
Timestamp: 1721953208 Timestamp [UCT]: 2024-07-26 00:20:08 Age [y:d:h:m:s]: 00:241:22:37:48
Block: 1073740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172822 RingCT/type: yes/0
Extra: 01f38063b95265eaac34d4a83111a4650c4922d203c2e2b8d48cd18b86d14b3611021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5798e82cb7ecfb594fb48a09d79f116739b4b77bb23a5c001d4a7da62c9618 0.600000000000 1546247 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1073750, "vin": [ { "gen": { "height": 1073740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5798e82cb7ecfb594fb48a09d79f116739b4b77bb23a5c001d4a7da62c9618" } } ], "extra": [ 1, 243, 128, 99, 185, 82, 101, 234, 172, 52, 212, 168, 49, 17, 164, 101, 12, 73, 34, 210, 3, 194, 226, 184, 212, 140, 209, 139, 134, 209, 75, 54, 17, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8