Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8b87032f6ec90a2bfe3af2080a0037c58c56eff8fa59fe5ea752016fa82b5f

Tx prefix hash: f3ab3b8eab090fe357d20cc843c2a70dd544b36269c9b9e5d91154e7242e826f
Tx public key: 121ce5aaf8bfe84498031c6b51a886f5e87a417df1f12145e8c85efd0b192a71
Timestamp: 1731198169 Timestamp [UCT]: 2024-11-10 00:22:49 Age [y:d:h:m:s]: 00:145:18:04:32
Block: 1150310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103990 RingCT/type: yes/0
Extra: 01121ce5aaf8bfe84498031c6b51a886f5e87a417df1f12145e8c85efd0b192a71021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7685dd0be398f50bca7d568f4788238c8d27fbb36a483f96c66a81999b47c9b 0.600000000000 1635583 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": 1150320, "vin": [ { "gen": { "height": 1150310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7685dd0be398f50bca7d568f4788238c8d27fbb36a483f96c66a81999b47c9b" } } ], "extra": [ 1, 18, 28, 229, 170, 248, 191, 232, 68, 152, 3, 28, 107, 81, 168, 134, 245, 232, 122, 65, 125, 241, 241, 33, 69, 232, 200, 94, 253, 11, 25, 42, 113, 2, 17, 0, 0, 0, 1, 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