Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f953a35fa2d0ce2e976b319d16eeed2e074896d66bc5874a18916e4ebc77a1

Tx prefix hash: 7980a7f8a3a7a00716850aef5560d3c3cc7189919e62b6def2218f18a6a8305f
Tx public key: 216753502f4a77d5fa606e8b2b772ddd13ca288308f1e997ff89076823abed1e
Timestamp: 1754965048 Timestamp [UCT]: 2025-08-12 02:17:28 Age [y:d:h:m:s]: 00:137:22:01:07
Block: 1345177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97910 RingCT/type: yes/0
Extra: 01216753502f4a77d5fa606e8b2b772ddd13ca288308f1e997ff89076823abed1e021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b76b83f940be3e9f1c469bbba370eaf9f23b9a85b60c595c5606bbc583f17e7 0.600000000000 1833066 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": 1345187, "vin": [ { "gen": { "height": 1345177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b76b83f940be3e9f1c469bbba370eaf9f23b9a85b60c595c5606bbc583f17e7" } } ], "extra": [ 1, 33, 103, 83, 80, 47, 74, 119, 213, 250, 96, 110, 139, 43, 119, 45, 221, 19, 202, 40, 131, 8, 241, 233, 151, 255, 137, 7, 104, 35, 171, 237, 30, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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