Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962d3699b9075954274bb3da405e66f6bf492e56fbf148d584938263979edb5e

Tx prefix hash: 0911f270020c20ccfbd0e41f5631ada3cc191ee6a6bde12022be00f7def196d7
Tx public key: 7a8b2b52c75f7a596b640b76dfb12f9a6bbd551b8f8ff8620c02e5abff64c7ef
Timestamp: 1717622416 Timestamp [UCT]: 2024-06-05 21:20:16 Age [y:d:h:m:s]: 00:283:05:46:32
Block: 1037841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202431 RingCT/type: yes/0
Extra: 017a8b2b52c75f7a596b640b76dfb12f9a6bbd551b8f8ff8620c02e5abff64c7ef0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eeb33a9a1cc8ae06e951d981bf8104e7f48db0cef24dd9a3d65a4a7dff3f708 0.600000000000 1506398 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": 1037851, "vin": [ { "gen": { "height": 1037841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eeb33a9a1cc8ae06e951d981bf8104e7f48db0cef24dd9a3d65a4a7dff3f708" } } ], "extra": [ 1, 122, 139, 43, 82, 199, 95, 122, 89, 107, 100, 11, 118, 223, 177, 47, 154, 107, 189, 85, 27, 143, 143, 248, 98, 12, 2, 229, 171, 255, 100, 199, 239, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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