Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c2dd67658655429a89dbd922099830c10c294f9f3cef99ccb27a91e650bf31a

Tx prefix hash: 0ca75a8dd2e0bbb2a9eca1b7800e87901bf559c37ec08f1afd020c54330d3917
Tx public key: 577e23eee1c402da323b383d6238581183d0038c2c9620c3fc158d4e4d08294c
Timestamp: 1626729813 Timestamp [UCT]: 2021-07-19 21:23:33 Age [y:d:h:m:s]: 03:299:20:20:29
Block: 297159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985748 RingCT/type: yes/0
Extra: 01577e23eee1c402da323b383d6238581183d0038c2c9620c3fc158d4e4d08294c021100000019c97064b9000000000000000000

1 output(s) for total of 63.590079961000 dcy

stealth address amount amount idx
00: c2ef3d8c5e28da43628c635a24dd8cc80cdddee40fd58418dd8e1dcd26e22ae0 63.590079961000 622005 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": 297169, "vin": [ { "gen": { "height": 297159 } } ], "vout": [ { "amount": 63590079961, "target": { "key": "c2ef3d8c5e28da43628c635a24dd8cc80cdddee40fd58418dd8e1dcd26e22ae0" } } ], "extra": [ 1, 87, 126, 35, 238, 225, 196, 2, 218, 50, 59, 56, 61, 98, 56, 88, 17, 131, 208, 3, 140, 44, 150, 32, 195, 252, 21, 141, 78, 77, 8, 41, 76, 2, 17, 0, 0, 0, 25, 201, 112, 100, 185, 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