Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7f07f2bb9221c31cba7fe8fab50c97c125a3d50393f97cf53f1b169daf479ab

Tx prefix hash: 65761583d125c9961d1b58154b8e663f5aee292a2102f592aff82575155b90e9
Tx public key: 5479f16ca3f8e4adfa0ecaf580f17cc47e653c5cdd7de1d2abc9824135b8dd68
Timestamp: 1700754205 Timestamp [UCT]: 2023-11-23 15:43:25 Age [y:d:h:m:s]: 01:146:20:03:01
Block: 898002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366119 RingCT/type: yes/0
Extra: 015479f16ca3f8e4adfa0ecaf580f17cc47e653c5cdd7de1d2abc9824135b8dd6802110000000333af99f4000000000000000000

1 output(s) for total of 0.649451287000 dcy

stealth address amount amount idx
00: e2b697cf42d85e74b607d68592c7cbca5292dd8baa29780bb57f6dcb32f1231e 0.649451287000 1354405 of 0

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": 898012, "vin": [ { "gen": { "height": 898002 } } ], "vout": [ { "amount": 649451287, "target": { "key": "e2b697cf42d85e74b607d68592c7cbca5292dd8baa29780bb57f6dcb32f1231e" } } ], "extra": [ 1, 84, 121, 241, 108, 163, 248, 228, 173, 250, 14, 202, 245, 128, 241, 124, 196, 126, 101, 60, 92, 221, 125, 225, 210, 171, 201, 130, 65, 53, 184, 221, 104, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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