Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ed64ac3224c70969132c273067fb6ea4dd5d190c87df595c6564896500abc9

Tx prefix hash: e7290d57fe7bc4673331caeefc7e4d07d24aa50a073f700d1a8ae5ac512e845f
Tx public key: daef58100a8777520258ce5ec572500f4650cc9b7458aa84cb0af7bbc5c26c3a
Timestamp: 1727819422 Timestamp [UCT]: 2024-10-01 21:50:22 Age [y:d:h:m:s]: 00:113:07:15:11
Block: 1122388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80958 RingCT/type: yes/0
Extra: 01daef58100a8777520258ce5ec572500f4650cc9b7458aa84cb0af7bbc5c26c3a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd095a9c5a4dde789e5f6bb1f9731474e9c55441fa35c3c0c3027ff3b06a983 0.600000000000 1604815 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": 1122398, "vin": [ { "gen": { "height": 1122388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd095a9c5a4dde789e5f6bb1f9731474e9c55441fa35c3c0c3027ff3b06a983" } } ], "extra": [ 1, 218, 239, 88, 16, 10, 135, 119, 82, 2, 88, 206, 94, 197, 114, 80, 15, 70, 80, 204, 155, 116, 88, 170, 132, 203, 10, 247, 187, 197, 194, 108, 58, 2, 17, 0, 0, 0, 2, 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