Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4ed8ecd51aa79d55e92a0fd77ada1ceae0513f5be8c067afcdaedcf5851799

Tx prefix hash: dab71ff9ab079ac7b4496fe430d8208c3d6e0e7a16089ad7471da761cf1075a1
Tx public key: afb752099f8cda3d546373044b7ea5da92987da5eb1cad8b990ac6b733d0b12d
Timestamp: 1723654397 Timestamp [UCT]: 2024-08-14 16:53:17 Age [y:d:h:m:s]: 01:084:17:16:41
Block: 1087848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319014 RingCT/type: yes/0
Extra: 01afb752099f8cda3d546373044b7ea5da92987da5eb1cad8b990ac6b733d0b12d02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df54442979e92782be0655acf7392d656fdb828b6dc1fe7ea1d9c0aba37da47 0.600000000000 1562459 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": 1087858, "vin": [ { "gen": { "height": 1087848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df54442979e92782be0655acf7392d656fdb828b6dc1fe7ea1d9c0aba37da47" } } ], "extra": [ 1, 175, 183, 82, 9, 159, 140, 218, 61, 84, 99, 115, 4, 75, 126, 165, 218, 146, 152, 125, 165, 235, 28, 173, 139, 153, 10, 198, 183, 51, 208, 177, 45, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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