Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e0452987f02a621f60cdbdd4d82e58441df53e9e0cd574e44e35be301be427

Tx prefix hash: 0ad4045bac9303f6dadd324c05a44657fb839dfe45e7deab078aebaceabfb7a9
Tx public key: bd1f419d66f4c83fb6eab4b4086044f8e6a18f3276b4052e5a35c381125dae4e
Timestamp: 1700703876 Timestamp [UCT]: 2023-11-23 01:44:36 Age [y:d:h:m:s]: 01:131:01:29:36
Block: 897574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354832 RingCT/type: yes/0
Extra: 01bd1f419d66f4c83fb6eab4b4086044f8e6a18f3276b4052e5a35c381125dae4e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.651575467000 dcy

stealth address amount amount idx
00: 1dd3547e059a74e2ae05be8848d6e83ac9a398c41f4ed70bca2f5df527beb0b8 0.651575467000 1353955 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": 897584, "vin": [ { "gen": { "height": 897574 } } ], "vout": [ { "amount": 651575467, "target": { "key": "1dd3547e059a74e2ae05be8848d6e83ac9a398c41f4ed70bca2f5df527beb0b8" } } ], "extra": [ 1, 189, 31, 65, 157, 102, 244, 200, 63, 182, 234, 180, 180, 8, 96, 68, 248, 230, 161, 143, 50, 118, 180, 5, 46, 90, 53, 195, 129, 18, 93, 174, 78, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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