Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abbfed5e66f363e58a8b21b376ca51b3e511ea030ce1601e665419a56de75bda

Tx prefix hash: fa7f134728a6672ab8886468920a48894e027665685f1893cc67136618decf1b
Tx public key: 44f6de9286e7357f0b8b6386cc210ef8cef65a83bc0ea4ed46a6cc27b6c9ad7a
Timestamp: 1764612350 Timestamp [UCT]: 2025-12-01 18:05:50 Age [y:d:h:m:s]: 00:021:21:29:08
Block: 1424280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15670 RingCT/type: yes/0
Extra: 0144f6de9286e7357f0b8b6386cc210ef8cef65a83bc0ea4ed46a6cc27b6c9ad7a02110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 948f809f0b4fdc60249c5d78d75d74765164eb8d251d814339ed25c9b8f17bb3 0.600000000000 1912911 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": 1424290, "vin": [ { "gen": { "height": 1424280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "948f809f0b4fdc60249c5d78d75d74765164eb8d251d814339ed25c9b8f17bb3" } } ], "extra": [ 1, 68, 246, 222, 146, 134, 231, 53, 127, 11, 139, 99, 134, 204, 33, 14, 248, 206, 246, 90, 131, 188, 14, 164, 237, 70, 166, 204, 39, 182, 201, 173, 122, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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