Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476b7c365fff02840782f4e58234e42384d3edfea171e007d48aa08577329511

Tx prefix hash: 16d654023a9d211fd1404b9a1b6deaa9f7c9576173b168b20dea037dd36bbb77
Tx public key: 842d45f1ba9a23ed8f4edde52901d8c17e25d69d8bb574bb54d5c5b1ff5117f3
Timestamp: 1754942133 Timestamp [UCT]: 2025-08-11 19:55:33 Age [y:d:h:m:s]: 00:096:20:41:37
Block: 1345012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68483 RingCT/type: yes/0
Extra: 01842d45f1ba9a23ed8f4edde52901d8c17e25d69d8bb574bb54d5c5b1ff5117f3021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06c7f79635e6b2839f1e287554772e5ad23a42fae66589b964a27fb40d93ff4 0.600000000000 1832901 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": 1345022, "vin": [ { "gen": { "height": 1345012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06c7f79635e6b2839f1e287554772e5ad23a42fae66589b964a27fb40d93ff4" } } ], "extra": [ 1, 132, 45, 69, 241, 186, 154, 35, 237, 143, 78, 221, 229, 41, 1, 216, 193, 126, 37, 214, 157, 139, 181, 116, 187, 84, 213, 197, 177, 255, 81, 23, 243, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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