Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4fe6863d6ff917ba7d3d4d90c48ca2f4651681e1559333d1f668701ef01edf

Tx prefix hash: d5b70a69dd2220429f5439b5a60bcf1b67c5504997d84d02eed75494a2de5f0a
Tx public key: 28d35d40301d312c99db974d5555355552e0a8dfab158d68b2c5d0c908e27c5e
Timestamp: 1763142600 Timestamp [UCT]: 2025-11-14 17:50:00 Age [y:d:h:m:s]: 00:077:10:40:34
Block: 1412102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55268 RingCT/type: yes/0
Extra: 0128d35d40301d312c99db974d5555355552e0a8dfab158d68b2c5d0c908e27c5e021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a7bfe456841558874d4793a1a4ec7e608138f423f84054e6d190d5dfa63198 0.600000000000 1900569 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": 1412112, "vin": [ { "gen": { "height": 1412102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a7bfe456841558874d4793a1a4ec7e608138f423f84054e6d190d5dfa63198" } } ], "extra": [ 1, 40, 211, 93, 64, 48, 29, 49, 44, 153, 219, 151, 77, 85, 85, 53, 85, 82, 224, 168, 223, 171, 21, 141, 104, 178, 197, 208, 201, 8, 226, 124, 94, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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