Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324180b506c43cde3b8d7603193bf7516d9de5ce652923ebf2a1f76b065cc563

Tx prefix hash: f26884f2c622a8e098a77a98b75bec480ba8853fe5b37ddc8983fb75d1564e28
Tx public key: bb4463288429adfe4c2a111eb36bdd5d72752bdf80e44b51b3d73e171fb9c7ee
Timestamp: 1715130506 Timestamp [UCT]: 2024-05-08 01:08:26 Age [y:d:h:m:s]: 00:315:14:39:36
Block: 1017184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225612 RingCT/type: yes/0
Extra: 01bb4463288429adfe4c2a111eb36bdd5d72752bdf80e44b51b3d73e171fb9c7ee0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46e6f41f1d94268dd4dc7f71264d56f46c9711ab734ad7ee12d9e6a115d67c2c 0.600000000000 1480951 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": 1017194, "vin": [ { "gen": { "height": 1017184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46e6f41f1d94268dd4dc7f71264d56f46c9711ab734ad7ee12d9e6a115d67c2c" } } ], "extra": [ 1, 187, 68, 99, 40, 132, 41, 173, 254, 76, 42, 17, 30, 179, 107, 221, 93, 114, 117, 43, 223, 128, 228, 75, 81, 179, 215, 62, 23, 31, 185, 199, 238, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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