Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948b1c6845352900c9a4c5cb6d222f51f0249891f1372fd2080dcf5782664b24

Tx prefix hash: 120554f4c6570a181d895aa3de64ab8fea3241ce7c1f8d0bac27e513dc2ea649
Tx public key: 37eff383bffa585cb3518f2fa14ae6ae34b642e5f2b0a00af640a96bf3de9bd1
Timestamp: 1736360325 Timestamp [UCT]: 2025-01-08 18:18:45 Age [y:d:h:m:s]: 00:072:23:23:55
Block: 1193056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51937 RingCT/type: yes/0
Extra: 0137eff383bffa585cb3518f2fa14ae6ae34b642e5f2b0a00af640a96bf3de9bd1021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88fe60133a6968fd115e0934595238ca6e4f5b6369c82c4c8fa04b9e0906a43 0.600000000000 1679613 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": 1193066, "vin": [ { "gen": { "height": 1193056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88fe60133a6968fd115e0934595238ca6e4f5b6369c82c4c8fa04b9e0906a43" } } ], "extra": [ 1, 55, 239, 243, 131, 191, 250, 88, 92, 179, 81, 143, 47, 161, 74, 230, 174, 52, 182, 66, 229, 242, 176, 160, 10, 246, 64, 169, 107, 243, 222, 155, 209, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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