Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780379217f66ce26d88194a3e3da8e591448d312db1f704ad340c9ec81ad7e41

Tx prefix hash: 4208d73d84ca981ce896add7def3847849d1f461ffad42eb250ebf4d1b215e6c
Tx public key: 638ce6acaaf9c3c9f4859218f0f09aad75d1aac0caf1a33e19f6e41a4121fc7c
Timestamp: 1719555032 Timestamp [UCT]: 2024-06-28 06:10:32 Age [y:d:h:m:s]: 00:344:22:31:28
Block: 1053869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246524 RingCT/type: yes/0
Extra: 01638ce6acaaf9c3c9f4859218f0f09aad75d1aac0caf1a33e19f6e41a4121fc7c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ab34a119abf6e5664e230ff84560c429d35e3f95ac9632c8b880619bb2bd438 0.600000000000 1524222 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": 1053879, "vin": [ { "gen": { "height": 1053869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ab34a119abf6e5664e230ff84560c429d35e3f95ac9632c8b880619bb2bd438" } } ], "extra": [ 1, 99, 140, 230, 172, 170, 249, 195, 201, 244, 133, 146, 24, 240, 240, 154, 173, 117, 209, 170, 192, 202, 241, 163, 62, 25, 246, 228, 26, 65, 33, 252, 124, 2, 17, 0, 0, 0, 5, 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