Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72fade686cc895d93daf49d0012d003e59c8d8db1c1f88f576b9c1d5695bfd8d

Tx prefix hash: 2721c0645092029cc269e6216a007ed36637f02f91dd2f6cbead637ea05d25f5
Tx public key: 0d8476696bd47ac99e2d8d5449f679e751129c59dd60b2f9a1fd4bd1219ea90a
Timestamp: 1713919664 Timestamp [UCT]: 2024-04-24 00:47:44 Age [y:d:h:m:s]: 00:205:09:50:00
Block: 1007139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147053 RingCT/type: yes/0
Extra: 010d8476696bd47ac99e2d8d5449f679e751129c59dd60b2f9a1fd4bd1219ea90a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f4ab469e5049d0a1579a89ab55a17e650e93f438ccc76e74fcc0efa262708c 0.600000000000 1468385 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": 1007149, "vin": [ { "gen": { "height": 1007139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f4ab469e5049d0a1579a89ab55a17e650e93f438ccc76e74fcc0efa262708c" } } ], "extra": [ 1, 13, 132, 118, 105, 107, 212, 122, 201, 158, 45, 141, 84, 73, 246, 121, 231, 81, 18, 156, 89, 221, 96, 178, 249, 161, 253, 75, 209, 33, 158, 169, 10, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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