Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893b1dd65b9e013eaf489dc479deef6c29dc25b1367a028db9bdbc358ca2bf50

Tx prefix hash: 0fe6f5e3093b5377f0d89114d4405d91db4537d13ca5f8a6d144178423e5a86d
Tx public key: 2cb1a7ff8ee2c678c211f8b186b413a619d7c1d7b81e776896a5f83b3e5695d3
Timestamp: 1680992306 Timestamp [UCT]: 2023-04-08 22:18:26 Age [y:d:h:m:s]: 02:210:07:22:09
Block: 734458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670123 RingCT/type: yes/0
Extra: 012cb1a7ff8ee2c678c211f8b186b413a619d7c1d7b81e776896a5f83b3e5695d30211000000015029cbac000000000000000000

1 output(s) for total of 2.261705134000 dcy

stealth address amount amount idx
00: 4ce9681b783601a152b4e8159ef0afc12fc6d8d82e65f540d328105d6eed47d4 2.261705134000 1180667 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": 734468, "vin": [ { "gen": { "height": 734458 } } ], "vout": [ { "amount": 2261705134, "target": { "key": "4ce9681b783601a152b4e8159ef0afc12fc6d8d82e65f540d328105d6eed47d4" } } ], "extra": [ 1, 44, 177, 167, 255, 142, 226, 198, 120, 194, 17, 248, 177, 134, 180, 19, 166, 25, 215, 193, 215, 184, 30, 119, 104, 150, 165, 248, 59, 62, 86, 149, 211, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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