Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b179a1488d19cd55f77f1cd3bf6a438e58bbd0b8a95d172bd8e681f702a2b50

Tx prefix hash: a9772193ec01b54f4124a3c397c3d9ab3a0605ebfa0e78e1db73fa5fe07c77f6
Tx public key: 59614456d403d5cb7a8c405dd1344c3927c9700ad068abac2a2e3cc8b6bd7aac
Timestamp: 1726085662 Timestamp [UCT]: 2024-09-11 20:14:22 Age [y:d:h:m:s]: 00:064:06:47:37
Block: 1108004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45945 RingCT/type: yes/0
Extra: 0159614456d403d5cb7a8c405dd1344c3927c9700ad068abac2a2e3cc8b6bd7aac02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d9a8b5bbe69b6d411eeb3ba72ac82a4d1cb61138b9f9bb59ecd5e77ea698fc4 0.600000000000 1585747 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": 1108014, "vin": [ { "gen": { "height": 1108004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d9a8b5bbe69b6d411eeb3ba72ac82a4d1cb61138b9f9bb59ecd5e77ea698fc4" } } ], "extra": [ 1, 89, 97, 68, 86, 212, 3, 213, 203, 122, 140, 64, 93, 209, 52, 76, 57, 39, 201, 112, 10, 208, 104, 171, 172, 42, 46, 60, 200, 182, 189, 122, 172, 2, 17, 0, 0, 0, 6, 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