Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f4a643cb61faabd9b9208baedf37579a6035962b035fe2553753b1bc250c68e

Tx prefix hash: d11385ffb32a56b510b7fa132f4975e58e36a4e89960ba07d999963c4d1fabc2
Tx public key: 89ca6dc7a609e5325026c554d4ee0e1a49b11cef03d35e117aa427771b3d5682
Timestamp: 1723179662 Timestamp [UCT]: 2024-08-09 05:01:02 Age [y:d:h:m:s]: 00:244:10:03:36
Block: 1083918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174575 RingCT/type: yes/0
Extra: 0189ca6dc7a609e5325026c554d4ee0e1a49b11cef03d35e117aa427771b3d568202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd174064f244051f6e9f5270b62e4bfa7922aeaa49253c01d0a4f2cd4f33e9b 0.600000000000 1558005 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": 1083928, "vin": [ { "gen": { "height": 1083918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd174064f244051f6e9f5270b62e4bfa7922aeaa49253c01d0a4f2cd4f33e9b" } } ], "extra": [ 1, 137, 202, 109, 199, 166, 9, 229, 50, 80, 38, 197, 84, 212, 238, 14, 26, 73, 177, 28, 239, 3, 211, 94, 17, 122, 164, 39, 119, 27, 61, 86, 130, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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