Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477a010b73dd854be274f11edda8cf5af798b3abfeda475c771fcb23f6ea6774

Tx prefix hash: 5bce8a2ba0365da5d370b8d469bd24c15d696ba199a426075a24fac5ea2a53d0
Tx public key: 4d8df45e7fdbc69c748582624fafc3b040ebff7a0927bb128f83a082beda15c9
Timestamp: 1719342169 Timestamp [UCT]: 2024-06-25 19:02:49 Age [y:d:h:m:s]: 01:137:05:23:46
Block: 1052089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356631 RingCT/type: yes/0
Extra: 014d8df45e7fdbc69c748582624fafc3b040ebff7a0927bb128f83a082beda15c90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad418f9533a2344a4d4f9dc193de242d33ec1ed0f86e9c1b4edf0cfaadfb5212 0.600000000000 1522410 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": 1052099, "vin": [ { "gen": { "height": 1052089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad418f9533a2344a4d4f9dc193de242d33ec1ed0f86e9c1b4edf0cfaadfb5212" } } ], "extra": [ 1, 77, 141, 244, 94, 127, 219, 198, 156, 116, 133, 130, 98, 79, 175, 195, 176, 64, 235, 255, 122, 9, 39, 187, 18, 143, 131, 160, 130, 190, 218, 21, 201, 2, 17, 0, 0, 0, 2, 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