Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825bc9a3b158b3cab87b92ed84c9b5d015e15f33c5f21650efae262c641da891

Tx prefix hash: 5aa954e0930f78f5f9d7767322bd6b8d709a6365c189110751d130d02a38c095
Tx public key: 434f5484e6141e7c07633fd3f9820e6be9a5ebe1e7c7093915789538173d640f
Timestamp: 1626373336 Timestamp [UCT]: 2021-07-15 18:22:16 Age [y:d:h:m:s]: 03:136:03:14:38
Block: 294676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 868426 RingCT/type: yes/0
Extra: 01434f5484e6141e7c07633fd3f9820e6be9a5ebe1e7c7093915789538173d640f021100000026a272b9cb000000000000000000

1 output(s) for total of 64.806204136000 dcy

stealth address amount amount idx
00: 5418fd13c454672924437c428fec4ffb51985bd62517514fd52cff615b067b46 64.806204136000 617242 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": 294686, "vin": [ { "gen": { "height": 294676 } } ], "vout": [ { "amount": 64806204136, "target": { "key": "5418fd13c454672924437c428fec4ffb51985bd62517514fd52cff615b067b46" } } ], "extra": [ 1, 67, 79, 84, 132, 230, 20, 30, 124, 7, 99, 63, 211, 249, 130, 14, 107, 233, 165, 235, 225, 231, 199, 9, 57, 21, 120, 149, 56, 23, 61, 100, 15, 2, 17, 0, 0, 0, 38, 162, 114, 185, 203, 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