Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 984b11acb6874c371e5b514b646393ea7a3fb32fe5c5b010754d9e479deec9dd

Tx prefix hash: b498965c516d82ac5fd43bd8da6af5e54a2f9e71fec0c9b0dd9797e287b90d9c
Tx public key: f89e026d5e3da1bb6509d649d91760c1b86f4e0bce5df8f5a463f95fdd547782
Timestamp: 1666456041 Timestamp [UCT]: 2022-10-22 16:27:21 Age [y:d:h:m:s]: 03:009:09:07:00
Block: 614669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 786944 RingCT/type: yes/0
Extra: 01f89e026d5e3da1bb6509d649d91760c1b86f4e0bce5df8f5a463f95fdd54778202110000000333af99f4000000000000000000

1 output(s) for total of 5.640875053000 dcy

stealth address amount amount idx
00: 1d8a073decc037d159d016550b9af788e8660f732f4beb81c19ce86fb1febef7 5.640875053000 1052068 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": 614679, "vin": [ { "gen": { "height": 614669 } } ], "vout": [ { "amount": 5640875053, "target": { "key": "1d8a073decc037d159d016550b9af788e8660f732f4beb81c19ce86fb1febef7" } } ], "extra": [ 1, 248, 158, 2, 109, 94, 61, 161, 187, 101, 9, 214, 73, 217, 23, 96, 193, 184, 111, 78, 11, 206, 93, 248, 245, 164, 99, 249, 95, 221, 84, 119, 130, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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