Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8745e9d6df7115bc7ac099c39f8b913390c02bcd647a48a14ffb6ef3b5c6ab64

Tx prefix hash: 96a288b48a487374ec114c628fa6662c07ed4fcbdd6c33bc7966a03770fa9534
Tx public key: dd2a515fea50d665746f1895558d32421f1e2b1d0c72933035587a30f0dbbdf0
Timestamp: 1726286286 Timestamp [UCT]: 2024-09-14 03:58:06 Age [y:d:h:m:s]: 00:071:13:54:37
Block: 1109661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51183 RingCT/type: yes/0
Extra: 01dd2a515fea50d665746f1895558d32421f1e2b1d0c72933035587a30f0dbbdf0021100000005e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 37d420b41cff14bcad4403376761d2a7378c0f73692b7d1630f0d0d03667eea8 0.608000000000 1587996 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": 1109671, "vin": [ { "gen": { "height": 1109661 } } ], "vout": [ { "amount": 608000000, "target": { "key": "37d420b41cff14bcad4403376761d2a7378c0f73692b7d1630f0d0d03667eea8" } } ], "extra": [ 1, 221, 42, 81, 95, 234, 80, 214, 101, 116, 111, 24, 149, 85, 141, 50, 66, 31, 30, 43, 29, 12, 114, 147, 48, 53, 88, 122, 48, 240, 219, 189, 240, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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