Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff43c4aebab161db7d14daae64ed81872f86d55fe206c6019b945c510611467

Tx prefix hash: 935a758b46a85f810d2eefbe37a62081c261825cc465dcfbbb715f702434e074
Tx public key: f0e73d910e64d5e6201e094d0a7d96ed0150f98081fc644fe206d93c5da1b3d0
Timestamp: 1762857374 Timestamp [UCT]: 2025-11-11 10:36:14 Age [y:d:h:m:s]: 00:009:08:22:06
Block: 1409742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6688 RingCT/type: yes/0
Extra: 01f0e73d910e64d5e6201e094d0a7d96ed0150f98081fc644fe206d93c5da1b3d002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f58f0b1aa04c7d1e481c2dfda8f2ba3226c66ce7d2f00d79d6d070b1461374 0.600000000000 1898189 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": 1409752, "vin": [ { "gen": { "height": 1409742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f58f0b1aa04c7d1e481c2dfda8f2ba3226c66ce7d2f00d79d6d070b1461374" } } ], "extra": [ 1, 240, 231, 61, 145, 14, 100, 213, 230, 32, 30, 9, 77, 10, 125, 150, 237, 1, 80, 249, 128, 129, 252, 100, 79, 226, 6, 217, 60, 93, 161, 179, 208, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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