Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b2f51fafad2dbdf5a0a9633bf39b860c1a8f4d14e546c6aee08fe0467fa6bb

Tx prefix hash: 5ca11e662ca6ab6da888c5bed70f066ab26c2f1dff5fa667805929b02701e758
Tx public key: 01043942888e80c4bdf6a4b74dbb26dbc20ee4d2238c76b2babdb127c1bfafb9
Timestamp: 1718876364 Timestamp [UCT]: 2024-06-20 09:39:24 Age [y:d:h:m:s]: 01:140:05:59:55
Block: 1048245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358781 RingCT/type: yes/0
Extra: 0101043942888e80c4bdf6a4b74dbb26dbc20ee4d2238c76b2babdb127c1bfafb902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dc7ed8715c047e6476213de6704c6ca935dfb9c728e9a645289af0f79ec7cf4 0.600000000000 1518282 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": 1048255, "vin": [ { "gen": { "height": 1048245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dc7ed8715c047e6476213de6704c6ca935dfb9c728e9a645289af0f79ec7cf4" } } ], "extra": [ 1, 1, 4, 57, 66, 136, 142, 128, 196, 189, 246, 164, 183, 77, 187, 38, 219, 194, 14, 228, 210, 35, 140, 118, 178, 186, 189, 177, 39, 193, 191, 175, 185, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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