Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77220c0c8fc924ba9957eac2d4c4a6a9d8e636aeb107c5e1cf9f3737fe7b786

Tx prefix hash: d3ec4b1a30b255898e9f6f8ec647f6ad0d5e20f219b5775e8c2d8e6457083373
Tx public key: be4111b51357ca78d429f1cb5cffb706a5d75fc61d75558301f470d3daec6892
Timestamp: 1735251721 Timestamp [UCT]: 2024-12-26 22:22:01 Age [y:d:h:m:s]: 00:085:00:50:23
Block: 1183871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60560 RingCT/type: yes/0
Extra: 01be4111b51357ca78d429f1cb5cffb706a5d75fc61d75558301f470d3daec689202110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc31f2b420e72c2c4af5a41e5c6d364e8a8897cef8050e0390e248f0f5f361b8 0.600000000000 1670320 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": 1183881, "vin": [ { "gen": { "height": 1183871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc31f2b420e72c2c4af5a41e5c6d364e8a8897cef8050e0390e248f0f5f361b8" } } ], "extra": [ 1, 190, 65, 17, 181, 19, 87, 202, 120, 212, 41, 241, 203, 92, 255, 183, 6, 165, 215, 95, 198, 29, 117, 85, 131, 1, 244, 112, 211, 218, 236, 104, 146, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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