Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 873cfc24292ee7b7989982868576d1ed2988e41cb2ff11351246f15eb300a4c0

Tx prefix hash: 03239ad2a74586733c92ddbb30c4e7e7b4d35a2b16ef61cca2fda7aa45b800e2
Tx public key: f6bfa42fc0335f68577d6a2d6fcff6621e75c88ef4e9f804be2823847b463dc0
Timestamp: 1719998912 Timestamp [UCT]: 2024-07-03 09:28:32 Age [y:d:h:m:s]: 00:273:07:55:00
Block: 1057547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195290 RingCT/type: yes/0
Extra: 01f6bfa42fc0335f68577d6a2d6fcff6621e75c88ef4e9f804be2823847b463dc00211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb039270c060b3b5c6035a2561cb4ec68eadc5d0afd90963d728b801ecae7da5 0.600000000000 1527984 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": 1057557, "vin": [ { "gen": { "height": 1057547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb039270c060b3b5c6035a2561cb4ec68eadc5d0afd90963d728b801ecae7da5" } } ], "extra": [ 1, 246, 191, 164, 47, 192, 51, 95, 104, 87, 125, 106, 45, 111, 207, 246, 98, 30, 117, 200, 142, 244, 233, 248, 4, 190, 40, 35, 132, 123, 70, 61, 192, 2, 17, 0, 0, 0, 6, 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