Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 407d73da3b0bf2a3f36e261654170517f408e535a532663bd1fba30a137cbd42

Tx prefix hash: f203d049f4402ac4b10ac896e50954912189b71702e39e929416258134cd62e5
Tx public key: 7c0ce5fe0e5f3e7686d6a54ec71ea40a0a1484c513c58162d9c85b6417569dc7
Timestamp: 1731239810 Timestamp [UCT]: 2024-11-10 11:56:50 Age [y:d:h:m:s]: 00:135:16:13:13
Block: 1150655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96770 RingCT/type: yes/0
Extra: 017c0ce5fe0e5f3e7686d6a54ec71ea40a0a1484c513c58162d9c85b6417569dc70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2ab605048b0a2f125940372cf0f7ac16011e6fa00a5e74951de4f1234329a51 0.600000000000 1636026 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": 1150665, "vin": [ { "gen": { "height": 1150655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ab605048b0a2f125940372cf0f7ac16011e6fa00a5e74951de4f1234329a51" } } ], "extra": [ 1, 124, 12, 229, 254, 14, 95, 62, 118, 134, 214, 165, 78, 199, 30, 164, 10, 10, 20, 132, 197, 19, 197, 129, 98, 217, 200, 91, 100, 23, 86, 157, 199, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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