Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42faa2c2fc96409b76cd4f8b1654a7f1674cae57e6a8e4572b60d3ffb731c2c8

Tx prefix hash: 5e303a57abaa358b8995076db0c3388b172e63ff646c3aae78a2cfecaf06e7cc
Tx public key: 4013ee81aa10c43f32ac90e2d14988a70d9e197f67f536a78b6c63c78de8d855
Timestamp: 1703499451 Timestamp [UCT]: 2023-12-25 10:17:31 Age [y:d:h:m:s]: 01:107:08:22:05
Block: 920753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337847 RingCT/type: yes/0
Extra: 014013ee81aa10c43f32ac90e2d14988a70d9e197f67f536a78b6c63c78de8d85502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a440440d5dbf2d13cbf0e8618c51deef1a615155e6f70938359c0ae75c391f30 0.600000000000 1378437 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": 920763, "vin": [ { "gen": { "height": 920753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a440440d5dbf2d13cbf0e8618c51deef1a615155e6f70938359c0ae75c391f30" } } ], "extra": [ 1, 64, 19, 238, 129, 170, 16, 196, 63, 50, 172, 144, 226, 209, 73, 136, 167, 13, 158, 25, 127, 103, 245, 54, 167, 139, 108, 99, 199, 141, 232, 216, 85, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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