Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c036a0d759f8da54f66edca14f4711bad94f18f365d4793fc074636975ad53

Tx prefix hash: 1eb1421798d85553c61aed32d470ab0b761d12f7bf219453d017b034a2d43bd3
Tx public key: 760deadaf547417d09086f21c6f3d5a0e2fb68fdc5d284cd22c985e660c8793e
Timestamp: 1724502956 Timestamp [UCT]: 2024-08-24 12:35:56 Age [y:d:h:m:s]: 00:244:01:59:02
Block: 1094904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174308 RingCT/type: yes/0
Extra: 01760deadaf547417d09086f21c6f3d5a0e2fb68fdc5d284cd22c985e660c8793e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50537d615300c58cf1a63fa3b63f50aced9df7c9ce9e9253756a22d84b602de9 0.600000000000 1570025 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": 1094914, "vin": [ { "gen": { "height": 1094904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50537d615300c58cf1a63fa3b63f50aced9df7c9ce9e9253756a22d84b602de9" } } ], "extra": [ 1, 118, 13, 234, 218, 245, 71, 65, 125, 9, 8, 111, 33, 198, 243, 213, 160, 226, 251, 104, 253, 197, 210, 132, 205, 34, 201, 133, 230, 96, 200, 121, 62, 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