Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70fea1bd7a43f584eaca0ddfd1c1762245aeaa1e80f690c96a9819923076fe8e

Tx prefix hash: 52e594834c73273a38d6c657d01e694492ffd211b63b5136bb62fe2a2c1f372a
Tx public key: c6d7e5785bc331131c7f7218d39498cb06a24bdaafef0ed1784b9a6d5c3ca872
Timestamp: 1732096813 Timestamp [UCT]: 2024-11-20 10:00:13 Age [y:d:h:m:s]: 00:125:14:44:32
Block: 1157739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89579 RingCT/type: yes/0
Extra: 01c6d7e5785bc331131c7f7218d39498cb06a24bdaafef0ed1784b9a6d5c3ca8720211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecc4beb78930c61a01dd5f74e1f0f3de345f284fc891b96ade6affd7c11030b5 0.600000000000 1643362 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": 1157749, "vin": [ { "gen": { "height": 1157739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecc4beb78930c61a01dd5f74e1f0f3de345f284fc891b96ade6affd7c11030b5" } } ], "extra": [ 1, 198, 215, 229, 120, 91, 195, 49, 19, 28, 127, 114, 24, 211, 148, 152, 203, 6, 162, 75, 218, 175, 239, 14, 209, 120, 75, 154, 109, 92, 60, 168, 114, 2, 17, 0, 0, 0, 4, 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