Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9842dd63147c1cd4c3b689eb0b2ece0719d2c35fd95d81ec15791668fa6f65ee

Tx prefix hash: 849428b740e8dc9299397fb084e9e65c10a3f005b45c05047d75068e487365a6
Tx public key: fec9cee066ed5fcebfa3736228ead5a6aa456f06d3e568bb1118ec22bd5f8e28
Timestamp: 1687160948 Timestamp [UCT]: 2023-06-19 07:49:08 Age [y:d:h:m:s]: 01:206:21:11:37
Block: 785554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409247 RingCT/type: yes/0
Extra: 01fec9cee066ed5fcebfa3736228ead5a6aa456f06d3e568bb1118ec22bd5f8e28021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.531558712000 dcy

stealth address amount amount idx
00: 16f858bdb023ca9f9bfedbd0d5085a4889d58b15b68d3db4dcb954d7c50f4bcb 1.531558712000 1235517 of 0

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": 785564, "vin": [ { "gen": { "height": 785554 } } ], "vout": [ { "amount": 1531558712, "target": { "key": "16f858bdb023ca9f9bfedbd0d5085a4889d58b15b68d3db4dcb954d7c50f4bcb" } } ], "extra": [ 1, 254, 201, 206, 224, 102, 237, 95, 206, 191, 163, 115, 98, 40, 234, 213, 166, 170, 69, 111, 6, 211, 229, 104, 187, 17, 24, 236, 34, 189, 95, 142, 40, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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