Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee1cd3fabd1869dafcedac8e3cdd7e25105caaa6be80c1b99b374c8eada1943

Tx prefix hash: 970c5733a90681c9edcb34097d7c13b21490592d41b53a6471d7658395cf6e41
Tx public key: ab6b6cabd0c70ee2e8debcf00e963e909483e0157d826270b1e83748a34c66d7
Timestamp: 1705557950 Timestamp [UCT]: 2024-01-18 06:05:50 Age [y:d:h:m:s]: 01:100:08:21:52
Block: 937793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332847 RingCT/type: yes/0
Extra: 01ab6b6cabd0c70ee2e8debcf00e963e909483e0157d826270b1e83748a34c66d70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a43e35b8606a4e77ff7d08bc91c6bc8f05010115bc52a4e9a5a363aac937f44a 0.600000000000 1395857 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": 937803, "vin": [ { "gen": { "height": 937793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a43e35b8606a4e77ff7d08bc91c6bc8f05010115bc52a4e9a5a363aac937f44a" } } ], "extra": [ 1, 171, 107, 108, 171, 208, 199, 14, 226, 232, 222, 188, 240, 14, 150, 62, 144, 148, 131, 224, 21, 125, 130, 98, 112, 177, 232, 55, 72, 163, 76, 102, 215, 2, 17, 0, 0, 0, 4, 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