Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ee24fd533750a55094b2c12a4771b9f7bf3b2e321546c5653d58d3c05b09d4a

Tx prefix hash: 8cc0f6dc5cb24062b0501c34aff27e393e823e8f8dc5daad3a5e1fd94a26bb45
Tx public key: 0ae2509ae04e5b96d7eab996fdc94a6b2002e59bce59b0787c4746b02425d7c8
Timestamp: 1716976319 Timestamp [UCT]: 2024-05-29 09:51:59 Age [y:d:h:m:s]: 00:352:10:23:01
Block: 1032492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251903 RingCT/type: yes/0
Extra: 010ae2509ae04e5b96d7eab996fdc94a6b2002e59bce59b0787c4746b02425d7c80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42cdad5b52b7577f7bea96e2de3a301dec5ca73df52ed51a6c3f9650083814e1 0.600000000000 1500945 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": 1032502, "vin": [ { "gen": { "height": 1032492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42cdad5b52b7577f7bea96e2de3a301dec5ca73df52ed51a6c3f9650083814e1" } } ], "extra": [ 1, 10, 226, 80, 154, 224, 78, 91, 150, 215, 234, 185, 150, 253, 201, 74, 107, 32, 2, 229, 155, 206, 89, 176, 120, 124, 71, 70, 176, 36, 37, 215, 200, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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