Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d300aea9f9f3e15366b80a6e248eacdd44bc7be35b30c810e5b9e9179d7e9dcc

Tx prefix hash: d4f73bcbe0ded54ea154774c5f4f434501100ca21ab3631e2508bb7e0262da32
Tx public key: 790c9c0a2db9a6e6ea29407640940aa43dda3701150d52f22d336c5e82ddee79
Timestamp: 1707908079 Timestamp [UCT]: 2024-02-14 10:54:39 Age [y:d:h:m:s]: 00:330:20:07:57
Block: 957301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236852 RingCT/type: yes/0
Extra: 01790c9c0a2db9a6e6ea29407640940aa43dda3701150d52f22d336c5e82ddee7902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34fbc5ac0bda4ff4d996c01186b72623e3e9c37444b03a9afbd66b0c754b923 0.600000000000 1416617 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": 957311, "vin": [ { "gen": { "height": 957301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34fbc5ac0bda4ff4d996c01186b72623e3e9c37444b03a9afbd66b0c754b923" } } ], "extra": [ 1, 121, 12, 156, 10, 45, 185, 166, 230, 234, 41, 64, 118, 64, 148, 10, 164, 61, 218, 55, 1, 21, 13, 82, 242, 45, 51, 108, 94, 130, 221, 238, 121, 2, 17, 0, 0, 0, 3, 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