Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c723554839126b35a353c79714e2ffc80f39e6c92dc6210684de2c7a9294c37d

Tx prefix hash: 7fcc211add3487ac52de17e1dc095086f4c67208861176c4b8c3957b7d525f2b
Tx public key: db07e7e61be97e610b1cd5d86768d29aef75c90ab7dd3c93480602aad9560e05
Timestamp: 1726976611 Timestamp [UCT]: 2024-09-22 03:43:31 Age [y:d:h:m:s]: 00:154:00:37:31
Block: 1115390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109865 RingCT/type: yes/0
Extra: 01db07e7e61be97e610b1cd5d86768d29aef75c90ab7dd3c93480602aad9560e0502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4fd771a32ecf70324e0f044b03181d2d32852efc14d62b83939be5c1428ab7e 0.600000000000 1595509 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": 1115400, "vin": [ { "gen": { "height": 1115390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4fd771a32ecf70324e0f044b03181d2d32852efc14d62b83939be5c1428ab7e" } } ], "extra": [ 1, 219, 7, 231, 230, 27, 233, 126, 97, 11, 28, 213, 216, 103, 104, 210, 154, 239, 117, 201, 10, 183, 221, 60, 147, 72, 6, 2, 170, 217, 86, 14, 5, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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