Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0995a57918c6aee25e83efa2f9195fe1905a42a7318b32bde82a488393646c37

Tx prefix hash: a6d4c262bfb56f85c44a9773f2aedd802fb61b501dd9b3eea7e3087c57a14f54
Tx public key: 4589b1cb4689afef13b731865dc74d812475a3adb4af2948aa221e7fce90890a
Timestamp: 1719504000 Timestamp [UCT]: 2024-06-27 16:00:00 Age [y:d:h:m:s]: 00:345:15:13:23
Block: 1053436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247033 RingCT/type: yes/0
Extra: 014589b1cb4689afef13b731865dc74d812475a3adb4af2948aa221e7fce90890a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d429a65179dd9a59cd3a2214bfa9e6d14cc251031237f77a080a55ffb544d8f 0.600000000000 1523783 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": 1053446, "vin": [ { "gen": { "height": 1053436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d429a65179dd9a59cd3a2214bfa9e6d14cc251031237f77a080a55ffb544d8f" } } ], "extra": [ 1, 69, 137, 177, 203, 70, 137, 175, 239, 19, 183, 49, 134, 93, 199, 77, 129, 36, 117, 163, 173, 180, 175, 41, 72, 170, 34, 30, 127, 206, 144, 137, 10, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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