Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f035580dd5c841226986e18d50d3090e15f21c7b3b0b5f92053c6ade58b056e8

Tx prefix hash: 52fb1e9eaa24ea2f6df536013667eff73955f9ac74f0ea3a2153fcd29b726676
Tx public key: 468a69986a00957c5b765f9f698082564c193d3f866f1980ea57026366906db3
Timestamp: 1673602143 Timestamp [UCT]: 2023-01-13 09:29:03 Age [y:d:h:m:s]: 02:087:13:42:05
Block: 673762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584251 RingCT/type: yes/0
Extra: 01468a69986a00957c5b765f9f698082564c193d3f866f1980ea57026366906db30211000000018b7b6602000000000000000000

1 output(s) for total of 3.593740830000 dcy

stealth address amount amount idx
00: 5f2a0f3f4a9dc9b4da56d579018636ab34db6c8ce92cc70c1f70bdfecb3da005 3.593740830000 1115385 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": 673772, "vin": [ { "gen": { "height": 673762 } } ], "vout": [ { "amount": 3593740830, "target": { "key": "5f2a0f3f4a9dc9b4da56d579018636ab34db6c8ce92cc70c1f70bdfecb3da005" } } ], "extra": [ 1, 70, 138, 105, 152, 106, 0, 149, 124, 91, 118, 95, 159, 105, 128, 130, 86, 76, 25, 61, 63, 134, 111, 25, 128, 234, 87, 2, 99, 102, 144, 109, 179, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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