Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345c5d893c72e4e31c0b9bb676062b57d59e092adde21cef3cbdcd71c4d7ab45

Tx prefix hash: 870d2da982d0b94ecb4047dca587f6befbce5f88ebdb4770769549023d76d94f
Tx public key: 8669260533512a2e20538d7c4c9388fc7473f480075bc5fa42620ea5ca5f5d66
Timestamp: 1760463419 Timestamp [UCT]: 2025-10-14 17:36:59 Age [y:d:h:m:s]: 00:029:03:33:30
Block: 1389901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20864 RingCT/type: yes/0
Extra: 018669260533512a2e20538d7c4c9388fc7473f480075bc5fa42620ea5ca5f5d660211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c6a0b0a136b81b6071c7aa23907c2b18dca54fcfd25681fb19fdc0a5504e5e1 0.600000000000 1878132 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": 1389911, "vin": [ { "gen": { "height": 1389901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c6a0b0a136b81b6071c7aa23907c2b18dca54fcfd25681fb19fdc0a5504e5e1" } } ], "extra": [ 1, 134, 105, 38, 5, 51, 81, 42, 46, 32, 83, 141, 124, 76, 147, 136, 252, 116, 115, 244, 128, 7, 91, 197, 250, 66, 98, 14, 165, 202, 95, 93, 102, 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