Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c62a378bfd918eaceb006175528852275f9a5c3e4ca65104f0cd487cbd48f2

Tx prefix hash: e81e2ed0e1988d83c23277d2b948f3159dba51e41da1fe56b8b55826e48f7a79
Tx public key: 52e726bbe3e8c93989bcc2ecc2ebf766c5121670128e6a6b729a46e671e66c23
Timestamp: 1721040718 Timestamp [UCT]: 2024-07-15 10:51:58 Age [y:d:h:m:s]: 00:335:21:52:21
Block: 1066192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239926 RingCT/type: yes/0
Extra: 0152e726bbe3e8c93989bcc2ecc2ebf766c5121670128e6a6b729a46e671e66c2302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64000d196f56ecd77ba4fc15c5b019c2275cb6ce35fd2df427a6305806cf5a2e 0.600000000000 1536765 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": 1066202, "vin": [ { "gen": { "height": 1066192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64000d196f56ecd77ba4fc15c5b019c2275cb6ce35fd2df427a6305806cf5a2e" } } ], "extra": [ 1, 82, 231, 38, 187, 227, 232, 201, 57, 137, 188, 194, 236, 194, 235, 247, 102, 197, 18, 22, 112, 18, 142, 106, 107, 114, 154, 70, 230, 113, 230, 108, 35, 2, 17, 0, 0, 0, 1, 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