Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 776a51b498eee87f3ea09a94cb5b8d7b7a1a21bbae902ef01508cdf1cc50ff7c

Tx prefix hash: dd22265c3f66761105da1b1eaf3c1310351c19d8358a01a0bf066c33f594521c
Tx public key: 922fa36ba73fe4e8e0866eee62ad9cf3b94e4c5e54a5217858c54a753f2a6490
Timestamp: 1719240879 Timestamp [UCT]: 2024-06-24 14:54:39 Age [y:d:h:m:s]: 00:215:18:40:27
Block: 1051242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154383 RingCT/type: yes/0
Extra: 01922fa36ba73fe4e8e0866eee62ad9cf3b94e4c5e54a5217858c54a753f2a64900211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74c44a32446786b76f014851357926d59da25bd978bed4a05d3c1ecb1209b07a 0.600000000000 1521551 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": 1051252, "vin": [ { "gen": { "height": 1051242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74c44a32446786b76f014851357926d59da25bd978bed4a05d3c1ecb1209b07a" } } ], "extra": [ 1, 146, 47, 163, 107, 167, 63, 228, 232, 224, 134, 110, 238, 98, 173, 156, 243, 185, 78, 76, 94, 84, 165, 33, 120, 88, 197, 74, 117, 63, 42, 100, 144, 2, 17, 0, 0, 0, 1, 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