Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8982bdfff3a9f7c21cd18857c6df70cd8f5e89e07888627782c00a03875a2d38

Tx prefix hash: e5f247c055393c3c02f1b1b81c28268fcca59d183098cfd98c159763c210027e
Tx public key: a6fba42c09c3990f6ae09563fc2348a3daa131809b401cc7ff62a88ec605949f
Timestamp: 1720730840 Timestamp [UCT]: 2024-07-11 20:47:20 Age [y:d:h:m:s]: 00:301:00:36:40
Block: 1063625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215072 RingCT/type: yes/0
Extra: 01a6fba42c09c3990f6ae09563fc2348a3daa131809b401cc7ff62a88ec605949f02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c75249971e14d85ec81f0cc0eaef1a9deb879447eb386d4ee2bfe8a94be32dd7 0.600000000000 1534142 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": 1063635, "vin": [ { "gen": { "height": 1063625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c75249971e14d85ec81f0cc0eaef1a9deb879447eb386d4ee2bfe8a94be32dd7" } } ], "extra": [ 1, 166, 251, 164, 44, 9, 195, 153, 15, 106, 224, 149, 99, 252, 35, 72, 163, 218, 161, 49, 128, 155, 64, 28, 199, 255, 98, 168, 142, 198, 5, 148, 159, 2, 17, 0, 0, 0, 11, 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