Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe35fc537b0940d63c28321ef810da1852281feccc6906a79f9b48fa01d884f0

Tx prefix hash: f1fe1d5b80be70c28982288ee072dc1643206aee5b50aac440a28607a42d30bf
Tx public key: b0acae0311a0d55d266e1dd72d8d2148b9aa378dc4b8022a0d7a830aed9ef8a7
Timestamp: 1762939225 Timestamp [UCT]: 2025-11-12 09:20:25 Age [y:d:h:m:s]: 00:041:03:06:42
Block: 1410412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29445 RingCT/type: yes/0
Extra: 01b0acae0311a0d55d266e1dd72d8d2148b9aa378dc4b8022a0d7a830aed9ef8a702110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b055a371150548de08ca4301aefb8a09597958d8a6df5185dc086215d4fcf6a 0.600000000000 1898863 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": 1410422, "vin": [ { "gen": { "height": 1410412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b055a371150548de08ca4301aefb8a09597958d8a6df5185dc086215d4fcf6a" } } ], "extra": [ 1, 176, 172, 174, 3, 17, 160, 213, 93, 38, 110, 29, 215, 45, 141, 33, 72, 185, 170, 55, 141, 196, 184, 2, 42, 13, 122, 131, 10, 237, 158, 248, 167, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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