Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e54adadf16f8f7cf30588cee3fcf084f9d29b593fc35ead8cc591dbfc90e0c

Tx prefix hash: 7a7e241d94080aee120c9155c30a38b68aaad0a5d385017ee1f3bd9b43215e91
Tx public key: df2ebcff4b4721503c3a7473abb9143d55c96093a331c5ce91429856d76a1b3b
Timestamp: 1737878076 Timestamp [UCT]: 2025-01-26 07:54:36 Age [y:d:h:m:s]: 00:046:09:23:17
Block: 1205579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32966 RingCT/type: yes/0
Extra: 01df2ebcff4b4721503c3a7473abb9143d55c96093a331c5ce91429856d76a1b3b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a51a1f787eb356d77d05687150e7291fec7b98c9b08892ef1d607e626e1b4503 0.600000000000 1692276 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": 1205589, "vin": [ { "gen": { "height": 1205579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a51a1f787eb356d77d05687150e7291fec7b98c9b08892ef1d607e626e1b4503" } } ], "extra": [ 1, 223, 46, 188, 255, 75, 71, 33, 80, 60, 58, 116, 115, 171, 185, 20, 61, 85, 201, 96, 147, 163, 49, 197, 206, 145, 66, 152, 86, 215, 106, 27, 59, 2, 17, 0, 0, 0, 4, 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