Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12b6d020bae2b16fe387298dc6e5d6dfc89d12af67b263e237162cceb4b3e580

Tx prefix hash: eff3552d745bd1b48110d173a1525d48f948911923b6e1f5b29549d56004d1d1
Tx public key: f7a6872fd9271badd314faf9620f9dd79e54587c9cc0e409b4b31d081790146e
Timestamp: 1752616391 Timestamp [UCT]: 2025-07-15 21:53:11 Age [y:d:h:m:s]: 00:174:03:00:49
Block: 1326291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123271 RingCT/type: yes/0
Extra: 01f7a6872fd9271badd314faf9620f9dd79e54587c9cc0e409b4b31d081790146e0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0432aa5fbbdbb6b28bdaf96aba78d267cf6e8384f2f3e7c39a109a196be8170d 0.600000000000 1814042 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": 1326301, "vin": [ { "gen": { "height": 1326291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0432aa5fbbdbb6b28bdaf96aba78d267cf6e8384f2f3e7c39a109a196be8170d" } } ], "extra": [ 1, 247, 166, 135, 47, 217, 39, 27, 173, 211, 20, 250, 249, 98, 15, 157, 215, 158, 84, 88, 124, 156, 192, 228, 9, 180, 179, 29, 8, 23, 144, 20, 110, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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