Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0d9d3a62425eb6b508b69d693c1d58b5287877e366b9a8146c962a0ef6c6b8

Tx prefix hash: f33691994037686f427aaffe8e9fc4f8ed579aa471d6b7d32f9b1e981bdd34a2
Tx public key: 0e0a2e4e040722958953209bd526cd0122bd7108d286567e321b688f0f4b108a
Timestamp: 1749971743 Timestamp [UCT]: 2025-06-15 07:15:43 Age [y:d:h:m:s]: 00:155:19:46:02
Block: 1305381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109145 RingCT/type: yes/0
Extra: 010e0a2e4e040722958953209bd526cd0122bd7108d286567e321b688f0f4b108a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ba6f0562947e5c33df49bc4abb798355b9655ac6a2ee998702087516808fdac 0.600000000000 1792980 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": 1305391, "vin": [ { "gen": { "height": 1305381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ba6f0562947e5c33df49bc4abb798355b9655ac6a2ee998702087516808fdac" } } ], "extra": [ 1, 14, 10, 46, 78, 4, 7, 34, 149, 137, 83, 32, 155, 213, 38, 205, 1, 34, 189, 113, 8, 210, 134, 86, 126, 50, 27, 104, 143, 15, 75, 16, 138, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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