Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9100329ea26bf5bcc648a85008a9e39451d0f49ddc029f0576a2c5cdb9d3dd

Tx prefix hash: d1fee69f063f5230c2e2cbe64f72d0612e8a0e57155d09869e1ee07e0e88fbfb
Tx public key: f2db4e6e8ce955c9611f37c3df78b3fddcb2db6640b187da5fc101069819bab3
Timestamp: 1715155424 Timestamp [UCT]: 2024-05-08 08:03:44 Age [y:d:h:m:s]: 00:248:09:42:15
Block: 1017406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177772 RingCT/type: yes/0
Extra: 01f2db4e6e8ce955c9611f37c3df78b3fddcb2db6640b187da5fc101069819bab30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6442685510a7331178995b214d91516b3fbef9205137f79d473bb529314e3a1c 0.600000000000 1481189 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": 1017416, "vin": [ { "gen": { "height": 1017406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6442685510a7331178995b214d91516b3fbef9205137f79d473bb529314e3a1c" } } ], "extra": [ 1, 242, 219, 78, 110, 140, 233, 85, 201, 97, 31, 55, 195, 223, 120, 179, 253, 220, 178, 219, 102, 64, 177, 135, 218, 95, 193, 1, 6, 152, 25, 186, 179, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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