Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6575cfaa20f6d960513f9d9973989d58eb6297023b45d06953a7bbe2833ae8f

Tx prefix hash: 2eed9011559688d9e883469bb843e14b157d0083865d177625df2ed066c20242
Tx public key: c1e333510d832cd7c12d361e6bd043017e3bf7a7bf68fa987ab339775a217fd9
Timestamp: 1744436849 Timestamp [UCT]: 2025-04-12 05:47:29 Age [y:d:h:m:s]: 00:272:01:18:20
Block: 1259644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192236 RingCT/type: yes/0
Extra: 01c1e333510d832cd7c12d361e6bd043017e3bf7a7bf68fa987ab339775a217fd90211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7ea1c8afc72d9b68aaa2e5548a5c8d1e66af39d0d119c958cb7860478f6fb0 0.600000000000 1746793 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": 1259654, "vin": [ { "gen": { "height": 1259644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7ea1c8afc72d9b68aaa2e5548a5c8d1e66af39d0d119c958cb7860478f6fb0" } } ], "extra": [ 1, 193, 227, 51, 81, 13, 131, 44, 215, 193, 45, 54, 30, 107, 208, 67, 1, 126, 59, 247, 167, 191, 104, 250, 152, 122, 179, 57, 119, 90, 33, 127, 217, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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