Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f22e776dddee1285d5d3904440a412043c1fde338821fa950215ea77ca5c4a7

Tx prefix hash: aa0cb1ebf08c742dbbc5da2c57218f7d806cd963544ca02e1794232f4e8e163b
Tx public key: ea4c8f4e3889506f0f50b025a23ff7a854f89368a474cb0b8b4e9bc8ab5fc9b9
Timestamp: 1750385326 Timestamp [UCT]: 2025-06-20 02:08:46 Age [y:d:h:m:s]: 00:153:20:19:13
Block: 1308753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107777 RingCT/type: yes/0
Extra: 01ea4c8f4e3889506f0f50b025a23ff7a854f89368a474cb0b8b4e9bc8ab5fc9b90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 366f825a2f589c0ed58c192d1a2a168e4b4ff575aeec119cfabefa1c5f4f6eff 0.600000000000 1796368 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": 1308763, "vin": [ { "gen": { "height": 1308753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "366f825a2f589c0ed58c192d1a2a168e4b4ff575aeec119cfabefa1c5f4f6eff" } } ], "extra": [ 1, 234, 76, 143, 78, 56, 137, 80, 111, 15, 80, 176, 37, 162, 63, 247, 168, 84, 248, 147, 104, 164, 116, 203, 11, 139, 78, 155, 200, 171, 95, 201, 185, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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