Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee60db0fc0d7af554c833bf07e8ec409cea592e328fd419cb3a614d42da56751

Tx prefix hash: 0cf4e7162d9c11de28dc0d86e46897c2dc9f35aaa5f4190ba91cfba0d804923d
Tx public key: 2ce1a20388e9fa4e0d12a30df5763ca138cab14916c0148d18e8d0fc2147020c
Timestamp: 1705457176 Timestamp [UCT]: 2024-01-17 02:06:16 Age [y:d:h:m:s]: 01:088:18:32:47
Block: 936960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324566 RingCT/type: yes/0
Extra: 012ce1a20388e9fa4e0d12a30df5763ca138cab14916c0148d18e8d0fc2147020c02110000002c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f93f75d589f7775a7bbbfa340599a9932596eae42c5a2b60bad93bd55bf7caa 0.600000000000 1395004 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": 936970, "vin": [ { "gen": { "height": 936960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f93f75d589f7775a7bbbfa340599a9932596eae42c5a2b60bad93bd55bf7caa" } } ], "extra": [ 1, 44, 225, 162, 3, 136, 233, 250, 78, 13, 18, 163, 13, 245, 118, 60, 161, 56, 202, 177, 73, 22, 192, 20, 141, 24, 232, 208, 252, 33, 71, 2, 12, 2, 17, 0, 0, 0, 44, 82, 212, 126, 148, 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