Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae20212374603929ab6bb72299c73704fab0b09de687e415d205e8f001746b3

Tx prefix hash: e924adefbc497c850517c111654f1fb8c88e019149596fa838ae18ae4cdf65d5
Tx public key: 1807ebd3721b8be7ce6b60364b2c2ad48e623ac2ba5d84af1db04ceeec9270d5
Timestamp: 1721043389 Timestamp [UCT]: 2024-07-15 11:36:29 Age [y:d:h:m:s]: 00:132:04:18:13
Block: 1066218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94578 RingCT/type: yes/0
Extra: 011807ebd3721b8be7ce6b60364b2c2ad48e623ac2ba5d84af1db04ceeec9270d5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4e570f7dfe9509a9ab8907a7b9e1e79f41946a9121b80a5c89962b884863c4f 0.600000000000 1536791 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": 1066228, "vin": [ { "gen": { "height": 1066218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4e570f7dfe9509a9ab8907a7b9e1e79f41946a9121b80a5c89962b884863c4f" } } ], "extra": [ 1, 24, 7, 235, 211, 114, 27, 139, 231, 206, 107, 96, 54, 75, 44, 42, 212, 142, 98, 58, 194, 186, 93, 132, 175, 29, 176, 76, 238, 236, 146, 112, 213, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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