Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213b08fcee1c0b83f6129fd6cca1287b6cbeec3128fc01229bfa453b3b5a9eef

Tx prefix hash: 06d88982b8e2fd3a0fee3ee47cb4ecd4b55f8f77fad733b12d41600c28bb931a
Tx public key: 03ccfa014798eb73e667adfeaf543e6ee6584f0973ab79e8cbdf03a0f9630774
Timestamp: 1685481154 Timestamp [UCT]: 2023-05-30 21:12:34 Age [y:d:h:m:s]: 02:161:01:38:11
Block: 771632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634883 RingCT/type: yes/0
Extra: 0103ccfa014798eb73e667adfeaf543e6ee6584f0973ab79e8cbdf03a0f9630774021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.703189754000 dcy

stealth address amount amount idx
00: 567c318c0c32bf3b46d0776f156733deb54d919a1c42ba0b6258e099226cb8eb 1.703189754000 1221005 of 0

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": 771642, "vin": [ { "gen": { "height": 771632 } } ], "vout": [ { "amount": 1703189754, "target": { "key": "567c318c0c32bf3b46d0776f156733deb54d919a1c42ba0b6258e099226cb8eb" } } ], "extra": [ 1, 3, 204, 250, 1, 71, 152, 235, 115, 230, 103, 173, 254, 175, 84, 62, 110, 230, 88, 79, 9, 115, 171, 121, 232, 203, 223, 3, 160, 249, 99, 7, 116, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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