Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c027930b7ec0abc7bd52994908b770b34862814feed6dba82c979b3d1412643

Tx prefix hash: 311c39faf523cf585610101143b765937cf9a2e45c882279c15fd740ac2f8732
Tx public key: f0282f4e44aaacb89d5203c0e405db12523ae2a8badcfa85f3a1f2f081d2a167
Timestamp: 1724040510 Timestamp [UCT]: 2024-08-19 04:08:30 Age [y:d:h:m:s]: 00:227:16:20:28
Block: 1091061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162579 RingCT/type: yes/0
Extra: 01f0282f4e44aaacb89d5203c0e405db12523ae2a8badcfa85f3a1f2f081d2a16702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a273b5ab2f386798c66982242babba33b852483d91a9d4eb0810e857d26950 0.600000000000 1565686 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": 1091071, "vin": [ { "gen": { "height": 1091061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a273b5ab2f386798c66982242babba33b852483d91a9d4eb0810e857d26950" } } ], "extra": [ 1, 240, 40, 47, 78, 68, 170, 172, 184, 157, 82, 3, 192, 228, 5, 219, 18, 82, 58, 226, 168, 186, 220, 250, 133, 243, 161, 242, 240, 129, 210, 161, 103, 2, 17, 0, 0, 0, 2, 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