Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eae63bd841d806fd14cbc447051172ed3c0f70f9135d8e178e81188a567580d

Tx prefix hash: de8aaf0a88739bf26ee69a30bf5434c1b49e057ad3ed56ba28d4878d319fd7d1
Tx public key: 579ae60d05d450e59e6f08309445d435b2483d89ffc11be5f2882a97a34c81a1
Timestamp: 1721329422 Timestamp [UCT]: 2024-07-18 19:03:42 Age [y:d:h:m:s]: 00:193:00:40:41
Block: 1068593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137843 RingCT/type: yes/0
Extra: 01579ae60d05d450e59e6f08309445d435b2483d89ffc11be5f2882a97a34c81a102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d272352c39d26a21c47bf3b1a7074e602c6aa99b7e728624d212d8d609e4778e 0.600000000000 1539682 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": 1068603, "vin": [ { "gen": { "height": 1068593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d272352c39d26a21c47bf3b1a7074e602c6aa99b7e728624d212d8d609e4778e" } } ], "extra": [ 1, 87, 154, 230, 13, 5, 212, 80, 229, 158, 111, 8, 48, 148, 69, 212, 53, 178, 72, 61, 137, 255, 193, 27, 229, 242, 136, 42, 151, 163, 76, 129, 161, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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