Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383f1d2dd825a150e6edd39e7a7630d3ca85b41a5ddb5dd505283cb220cb4bbc

Tx prefix hash: 810d786931b369c64d8e149a838a1434aa1fc9878070a9ca73b754e3db7ca638
Tx public key: a646158e22be3c80cb72c4ecacab84527227cdb4d726038e2e6c9b5320cbc575
Timestamp: 1677831861 Timestamp [UCT]: 2023-03-03 08:24:21 Age [y:d:h:m:s]: 01:337:18:23:38
Block: 708844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502065 RingCT/type: yes/0
Extra: 01a646158e22be3c80cb72c4ecacab84527227cdb4d726038e2e6c9b5320cbc575021100000004835e4d22000000000000000000

1 output(s) for total of 2.749827641000 dcy

stealth address amount amount idx
00: b4ad17eefdd04e444f85e0a8f5a12d9c0ec694fe9cdf553ec1f240664676564c 2.749827641000 1152763 of 0

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": 708854, "vin": [ { "gen": { "height": 708844 } } ], "vout": [ { "amount": 2749827641, "target": { "key": "b4ad17eefdd04e444f85e0a8f5a12d9c0ec694fe9cdf553ec1f240664676564c" } } ], "extra": [ 1, 166, 70, 21, 142, 34, 190, 60, 128, 203, 114, 196, 236, 172, 171, 132, 82, 114, 39, 205, 180, 215, 38, 3, 142, 46, 108, 155, 83, 32, 203, 197, 117, 2, 17, 0, 0, 0, 4, 131, 94, 77, 34, 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