Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d5066f29911763454d5668b0d1da60002317d0aa498e9fc214ce2669152e62

Tx prefix hash: e65056013d9f19aeb5a384001bf532c5ff8083f6168b1a9ac9bc131611760243
Tx public key: f825fc8892fcf2598456a6db700c510a4b8be44b5a2b43f210317a9e6230fa3b
Timestamp: 1688382196 Timestamp [UCT]: 2023-07-03 11:03:16 Age [y:d:h:m:s]: 01:350:11:55:01
Block: 795686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511560 RingCT/type: yes/0
Extra: 01f825fc8892fcf2598456a6db700c510a4b8be44b5a2b43f210317a9e6230fa3b02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.417627447000 dcy

stealth address amount amount idx
00: f64aa2e35288c83923a119162d1394e3b15ddc72b8ca4e4b5272087920981650 1.417627447000 1246509 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": 795696, "vin": [ { "gen": { "height": 795686 } } ], "vout": [ { "amount": 1417627447, "target": { "key": "f64aa2e35288c83923a119162d1394e3b15ddc72b8ca4e4b5272087920981650" } } ], "extra": [ 1, 248, 37, 252, 136, 146, 252, 242, 89, 132, 86, 166, 219, 112, 12, 81, 10, 75, 139, 228, 75, 90, 43, 67, 242, 16, 49, 122, 158, 98, 48, 250, 59, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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