Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2265d20a21d4b06578ce06c0f4e5aad9270f708b2c5374b37569f9717d2ddb2

Tx prefix hash: 348f35a5bccc10193c719d5b77596e63de39585797d563743f439cb84bcc7b3d
Tx public key: 4cac0580b0a40fadf66cb52bc78ddb67934e026cf0862b442c6c2e28d5c88b11
Timestamp: 1765078516 Timestamp [UCT]: 2025-12-07 03:35:16 Age [y:d:h:m:s]: 00:015:02:10:58
Block: 1428147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10800 RingCT/type: yes/0
Extra: 014cac0580b0a40fadf66cb52bc78ddb67934e026cf0862b442c6c2e28d5c88b110211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43a49a25d6fef5146b8563d09bfb37ddfde10d770c2d727361b89f048a6da2dd 0.600000000000 1916856 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": 1428157, "vin": [ { "gen": { "height": 1428147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43a49a25d6fef5146b8563d09bfb37ddfde10d770c2d727361b89f048a6da2dd" } } ], "extra": [ 1, 76, 172, 5, 128, 176, 164, 15, 173, 246, 108, 181, 43, 199, 141, 219, 103, 147, 78, 2, 108, 240, 134, 43, 68, 44, 108, 46, 40, 213, 200, 139, 17, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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