Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e9081f8b0b0d0ae90012960d5949784f2b6b33fbf06cf7487b4bef719e5e837

Tx prefix hash: 2422fbaa930c723a0292402cc5656a8bd9f64bff243354c71ec03f8becf66f10
Tx public key: 642c8b3e25fbb86d52b7d21e6338969477ec32fdb30b56a5673cb943b309a143
Timestamp: 1712328824 Timestamp [UCT]: 2024-04-05 14:53:44 Age [y:d:h:m:s]: 01:040:20:22:55
Block: 993932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290189 RingCT/type: yes/0
Extra: 01642c8b3e25fbb86d52b7d21e6338969477ec32fdb30b56a5673cb943b309a14302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc3cb6021600814d9c9446383dbce456576b9e4c1aa3d4501df9161747f8d0d 0.600000000000 1454328 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": 993942, "vin": [ { "gen": { "height": 993932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc3cb6021600814d9c9446383dbce456576b9e4c1aa3d4501df9161747f8d0d" } } ], "extra": [ 1, 100, 44, 139, 62, 37, 251, 184, 109, 82, 183, 210, 30, 99, 56, 150, 148, 119, 236, 50, 253, 179, 11, 86, 165, 103, 60, 185, 67, 179, 9, 161, 67, 2, 17, 0, 0, 0, 1, 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