Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766b740bf83b004c373f70777f050712c67a08611bc22f1e994d05451c1e7f39

Tx prefix hash: 68be2cce63d58f4d276c54fc231efa333e870950a8c3eedd53ddbd698d490c2d
Tx public key: eb4fd575f19d3ab73b496b74770e8cc92627adb28fb5a54bfe786b62ed8cf320
Timestamp: 1704009147 Timestamp [UCT]: 2023-12-31 07:52:27 Age [y:d:h:m:s]: 01:146:13:44:25
Block: 924972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365907 RingCT/type: yes/0
Extra: 01eb4fd575f19d3ab73b496b74770e8cc92627adb28fb5a54bfe786b62ed8cf3200211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 639573f722cea6a0ed867c7a8d68521b695a7fa9f4b5b63c77b7d9451516b5c4 0.600000000000 1382732 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": 924982, "vin": [ { "gen": { "height": 924972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639573f722cea6a0ed867c7a8d68521b695a7fa9f4b5b63c77b7d9451516b5c4" } } ], "extra": [ 1, 235, 79, 213, 117, 241, 157, 58, 183, 59, 73, 107, 116, 119, 14, 140, 201, 38, 39, 173, 178, 143, 181, 165, 75, 254, 120, 107, 98, 237, 140, 243, 32, 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