Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60102485806d0432db56f5c4a07ef51293aa1796386a1810d7a577a6fe0bb510

Tx prefix hash: 016604afc5e3b7a065f147619885ee1fe079cc912086747359fff0c2c9c248e7
Tx public key: b7a20a833781c8d0ebd572c431ccd5d54405132f4647e2bcbce26c41d47e594f
Timestamp: 1726325119 Timestamp [UCT]: 2024-09-14 14:45:19 Age [y:d:h:m:s]: 00:074:15:12:40
Block: 1109992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53361 RingCT/type: yes/0
Extra: 01b7a20a833781c8d0ebd572c431ccd5d54405132f4647e2bcbce26c41d47e594f021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804e52f9fb41440d3b2d8a822a5ef871c6577cc33a575e5ba973c44be5d7c96e 0.600000000000 1588439 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": 1110002, "vin": [ { "gen": { "height": 1109992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804e52f9fb41440d3b2d8a822a5ef871c6577cc33a575e5ba973c44be5d7c96e" } } ], "extra": [ 1, 183, 162, 10, 131, 55, 129, 200, 208, 235, 213, 114, 196, 49, 204, 213, 213, 68, 5, 19, 47, 70, 71, 226, 188, 188, 226, 108, 65, 212, 126, 89, 79, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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