Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca2c40a1940bd765274dadb4381f9932e5d78b92951ad76295e1a77686e8716

Tx prefix hash: fe056f386efd7e61b7b2d3236837484f0db139c643d68cff28f4200caf6cfa4b
Tx public key: c1efd714754c329ab375a2445f7ca2879de8d8b41f894e03b5a48b3ad1cc5415
Timestamp: 1744967044 Timestamp [UCT]: 2025-04-18 09:04:04 Age [y:d:h:m:s]: 00:216:19:14:00
Block: 1264037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152661 RingCT/type: yes/0
Extra: 01c1efd714754c329ab375a2445f7ca2879de8d8b41f894e03b5a48b3ad1cc54150211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808dab97480b9b325d8e639af7d7e7cc68e6631f2dd8e141b622f4bef9ac2a90 0.600000000000 1751230 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": 1264047, "vin": [ { "gen": { "height": 1264037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808dab97480b9b325d8e639af7d7e7cc68e6631f2dd8e141b622f4bef9ac2a90" } } ], "extra": [ 1, 193, 239, 215, 20, 117, 76, 50, 154, 179, 117, 162, 68, 95, 124, 162, 135, 157, 232, 216, 180, 31, 137, 78, 3, 181, 164, 139, 58, 209, 204, 84, 21, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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