Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a71117fff95d8b026ab31d80aee20f5f9bc5c13c9e0aace5f1289b950dea0c6

Tx prefix hash: 716c0bc7522e8123c8a39cfaf10a92663b6ba3b267272e41782b96af810a6328
Tx public key: 23c1c0e4a52c32fde96124217477cf00b83dd8fa6f59a1ddb144e70560c317fa
Timestamp: 1765361893 Timestamp [UCT]: 2025-12-10 10:18:13 Age [y:d:h:m:s]: 00:053:02:07:58
Block: 1430490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37829 RingCT/type: yes/0
Extra: 0123c1c0e4a52c32fde96124217477cf00b83dd8fa6f59a1ddb144e70560c317fa02110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad8933f70498925fa9a2144ce20e8ee326b68eff40dc4d5c3fd08867a3b5c48 0.600000000000 1919241 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": 1430500, "vin": [ { "gen": { "height": 1430490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad8933f70498925fa9a2144ce20e8ee326b68eff40dc4d5c3fd08867a3b5c48" } } ], "extra": [ 1, 35, 193, 192, 228, 165, 44, 50, 253, 233, 97, 36, 33, 116, 119, 207, 0, 184, 61, 216, 250, 111, 89, 161, 221, 177, 68, 231, 5, 96, 195, 23, 250, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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