Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c806906f013035867247522f7435ef87b05296aef350a995e1c427f57ab1c22

Tx prefix hash: c95669ec239601f403445f3e239a0d80f54b698c2c55350cd28792db92a3076e
Tx public key: 1b483f9f89f7dc2406634e391b6f378f003c1c35d97e7725c5d938a6c9bc262d
Timestamp: 1760224004 Timestamp [UCT]: 2025-10-11 23:06:44 Age [y:d:h:m:s]: 00:034:01:49:59
Block: 1387909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24408 RingCT/type: yes/0
Extra: 011b483f9f89f7dc2406634e391b6f378f003c1c35d97e7725c5d938a6c9bc262d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 602ef1bc4a045eac70df08d767d21aaa0d76977cff94a2fe220ba1b1803e9cb5 0.600000000000 1876104 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": 1387919, "vin": [ { "gen": { "height": 1387909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "602ef1bc4a045eac70df08d767d21aaa0d76977cff94a2fe220ba1b1803e9cb5" } } ], "extra": [ 1, 27, 72, 63, 159, 137, 247, 220, 36, 6, 99, 78, 57, 27, 111, 55, 143, 0, 60, 28, 53, 217, 126, 119, 37, 197, 217, 56, 166, 201, 188, 38, 45, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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