Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e464f0e6af2ffb0790ded93cec7c7b4b91a057aec0bd05be417af7d106d14f2

Tx prefix hash: dd27d72251bb8f6f33dd4c283afd36305e5ebc831c8ca4899510e5a18571588e
Tx public key: 0de2844d023f43d4781d01a08058be25b631a4c5d0f1e5bd68d686bbf6907882
Timestamp: 1745684444 Timestamp [UCT]: 2025-04-26 16:20:44 Age [y:d:h:m:s]: 00:208:11:41:50
Block: 1269981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146709 RingCT/type: yes/0
Extra: 010de2844d023f43d4781d01a08058be25b631a4c5d0f1e5bd68d686bbf690788202110000000588cd2b63000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6184dd822acb9610a3ac4df598ccbcc98675414db8184e53796ed3a0f4acc7c5 0.600000000000 1757220 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": 1269991, "vin": [ { "gen": { "height": 1269981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6184dd822acb9610a3ac4df598ccbcc98675414db8184e53796ed3a0f4acc7c5" } } ], "extra": [ 1, 13, 226, 132, 77, 2, 63, 67, 212, 120, 29, 1, 160, 128, 88, 190, 37, 182, 49, 164, 197, 208, 241, 229, 189, 104, 214, 134, 187, 246, 144, 120, 130, 2, 17, 0, 0, 0, 5, 136, 205, 43, 99, 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