Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7872aa7cfef13a98d956d5c628865dbeafb7a5033e018844228d340c762319db

Tx prefix hash: e940f963ca09ff4a69e1aeb78ee0fa3dda3075a33bebaa8add206efbceb22243
Tx public key: 27b35814e4f7fb527742a9bbc7b0bd10f7c04a478de57b9f0b959789b6207be8
Timestamp: 1746606936 Timestamp [UCT]: 2025-05-07 08:35:36 Age [y:d:h:m:s]: 00:188:13:30:28
Block: 1277611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132472 RingCT/type: yes/0
Extra: 0127b35814e4f7fb527742a9bbc7b0bd10f7c04a478de57b9f0b959789b6207be80211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c45e2d05ce73afd8c6669aedc1bd1251d60733e7e2bf1cfd9a72fee506ca29e7 0.600000000000 1764968 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": 1277621, "vin": [ { "gen": { "height": 1277611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c45e2d05ce73afd8c6669aedc1bd1251d60733e7e2bf1cfd9a72fee506ca29e7" } } ], "extra": [ 1, 39, 179, 88, 20, 228, 247, 251, 82, 119, 66, 169, 187, 199, 176, 189, 16, 247, 192, 74, 71, 141, 229, 123, 159, 11, 149, 151, 137, 182, 32, 123, 232, 2, 17, 0, 0, 0, 7, 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