Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc55349e843f8c1a09154a8e6f99281578efdbf46dfa5b433ff0d3a45da0cf8

Tx prefix hash: bf28b8c596acad6d526580a36187fa69721bcfcdd0333e5a8e70127fdcea86a1
Tx public key: a05c23017d26bf99158b4de467c44838d4edf407d93cb5a8e8c7dd2801e13e5d
Timestamp: 1763315331 Timestamp [UCT]: 2025-11-16 17:48:51 Age [y:d:h:m:s]: 00:054:23:04:04
Block: 1413530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39367 RingCT/type: yes/0
Extra: 01a05c23017d26bf99158b4de467c44838d4edf407d93cb5a8e8c7dd2801e13e5d02110000000417b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afb296d042ea380ad4d57095fd4c329c0f110ab7ef664ef7d490b73d731f0dc4 0.600000000000 1902009 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": 1413540, "vin": [ { "gen": { "height": 1413530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afb296d042ea380ad4d57095fd4c329c0f110ab7ef664ef7d490b73d731f0dc4" } } ], "extra": [ 1, 160, 92, 35, 1, 125, 38, 191, 153, 21, 139, 77, 228, 103, 196, 72, 56, 212, 237, 244, 7, 217, 60, 181, 168, 232, 199, 221, 40, 1, 225, 62, 93, 2, 17, 0, 0, 0, 4, 23, 177, 145, 50, 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