Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b922346bb9977cad6b2d2308ea3292587d3917ea81f4875d79c3ef078a162c0a

Tx prefix hash: adac9dd826d9672b053c1615d822312daef4705f41088026167dfefa23a5b446
Tx public key: feab1625f275634d013f1fb86f1049ca468749d511b6f4497a5daad5e98d5d97
Timestamp: 1746251507 Timestamp [UCT]: 2025-05-03 05:51:47 Age [y:d:h:m:s]: 00:202:06:09:17
Block: 1274678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142255 RingCT/type: yes/0
Extra: 01feab1625f275634d013f1fb86f1049ca468749d511b6f4497a5daad5e98d5d970211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571a99b3bdb9878ff4d4d9aeb36aa5104e12be5ee6cbd28773fb8047d0c9f1b6 0.600000000000 1761977 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": 1274688, "vin": [ { "gen": { "height": 1274678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571a99b3bdb9878ff4d4d9aeb36aa5104e12be5ee6cbd28773fb8047d0c9f1b6" } } ], "extra": [ 1, 254, 171, 22, 37, 242, 117, 99, 77, 1, 63, 31, 184, 111, 16, 73, 202, 70, 135, 73, 213, 17, 182, 244, 73, 122, 93, 170, 213, 233, 141, 93, 151, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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