Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4eb96f959c41805eca2be33884bf377f08902dabcd428160e0f9384e878accb

Tx prefix hash: 0267c15d1191f7101bdaf2e9c67153df4a4cff840d2c497838b917b4bdeac3c1
Tx public key: 3b5a57f244201112c32278fe0e630f8ef8383ff658b8c7880c0d98a65de2a764
Timestamp: 1619430932 Timestamp [UCT]: 2021-04-26 09:55:32 Age [y:d:h:m:s]: 04:192:17:09:37
Block: 248137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156368 RingCT/type: yes/0
Extra: 013b5a57f244201112c32278fe0e630f8ef8383ff658b8c7880c0d98a65de2a76402110000002590ec05ad000000000000000000

1 output(s) for total of 92.438779889000 dcy

stealth address amount amount idx
00: f0bc902b298d9017e1a6496fa8ebd5ec963e2d5d500c6e63186150f44bb4c9fd 92.438779889000 519488 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": 248147, "vin": [ { "gen": { "height": 248137 } } ], "vout": [ { "amount": 92438779889, "target": { "key": "f0bc902b298d9017e1a6496fa8ebd5ec963e2d5d500c6e63186150f44bb4c9fd" } } ], "extra": [ 1, 59, 90, 87, 242, 68, 32, 17, 18, 195, 34, 120, 254, 14, 99, 15, 142, 248, 56, 63, 246, 88, 184, 199, 136, 12, 13, 152, 166, 93, 226, 167, 100, 2, 17, 0, 0, 0, 37, 144, 236, 5, 173, 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