Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091abeb4a2dc9c5fd1100628a60bceec6466f11bd5e6bbce488c2e2bf6856d54

Tx prefix hash: 9ef0af765a644dbfa7014ab41f4f1eff98713efc28b9473e5c4bbec946d02fd2
Tx public key: 4ff6ce8c6f8368d6a156e31fc70d0cf632976da68f70ce7866a4ac6438b9778a
Timestamp: 1759839970 Timestamp [UCT]: 2025-10-07 12:26:10 Age [y:d:h:m:s]: 00:033:12:00:25
Block: 1384728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23992 RingCT/type: yes/0
Extra: 014ff6ce8c6f8368d6a156e31fc70d0cf632976da68f70ce7866a4ac6438b9778a021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be50e7fbf75ab38e636a7b1c1828e64b97bb5a17b2baa9525beb9f74f06fd60e 0.600000000000 1872881 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": 1384738, "vin": [ { "gen": { "height": 1384728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be50e7fbf75ab38e636a7b1c1828e64b97bb5a17b2baa9525beb9f74f06fd60e" } } ], "extra": [ 1, 79, 246, 206, 140, 111, 131, 104, 214, 161, 86, 227, 31, 199, 13, 12, 246, 50, 151, 109, 166, 143, 112, 206, 120, 102, 164, 172, 100, 56, 185, 119, 138, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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