Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b60290e7a41e999bd562aead4a3a15ee313dfdddfa0fd1f004e7529e53572f

Tx prefix hash: f7e610382d9ad1c9ce7ddc4dd895ea6c6ea04f310fb4988a63bd660663eaaef9
Tx public key: 4fcee594f58c49e7d06d0a4a78ab99ee52ea2d04400bfab6d8dbb1a1d1b0293b
Timestamp: 1744195371 Timestamp [UCT]: 2025-04-09 10:42:51 Age [y:d:h:m:s]: 00:225:09:50:12
Block: 1257651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158820 RingCT/type: yes/0
Extra: 014fcee594f58c49e7d06d0a4a78ab99ee52ea2d04400bfab6d8dbb1a1d1b0293b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a3b4405429b63ab31dd0c968b9de40b1e0f7117579e0dc38f9d93ee51c2cc03 0.600000000000 1744778 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": 1257661, "vin": [ { "gen": { "height": 1257651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a3b4405429b63ab31dd0c968b9de40b1e0f7117579e0dc38f9d93ee51c2cc03" } } ], "extra": [ 1, 79, 206, 229, 148, 245, 140, 73, 231, 208, 109, 10, 74, 120, 171, 153, 238, 82, 234, 45, 4, 64, 11, 250, 182, 216, 219, 177, 161, 209, 176, 41, 59, 2, 17, 0, 0, 0, 2, 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