Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030fd2e14202374e60b9cefbafe0942829549810a5531fd51ae435648de0ccc3

Tx prefix hash: 640060f1c5a080affeea669991a2e1512c98d5ad0505a304f98b04d6e660e16b
Tx public key: dd397cd169571d0c19b384d8b6956dc0f3dcb291fabb04adc71c020b03b64abc
Timestamp: 1708775380 Timestamp [UCT]: 2024-02-24 11:49:40 Age [y:d:h:m:s]: 01:040:00:44:09
Block: 964503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289624 RingCT/type: yes/0
Extra: 01dd397cd169571d0c19b384d8b6956dc0f3dcb291fabb04adc71c020b03b64abc021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 463964513c4f53218368decf0d73f12e9fa292c2563f8c43c55fc00c3b4d8c28 0.600000000000 1424244 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": 964513, "vin": [ { "gen": { "height": 964503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "463964513c4f53218368decf0d73f12e9fa292c2563f8c43c55fc00c3b4d8c28" } } ], "extra": [ 1, 221, 57, 124, 209, 105, 87, 29, 12, 25, 179, 132, 216, 182, 149, 109, 192, 243, 220, 178, 145, 250, 187, 4, 173, 199, 28, 2, 11, 3, 182, 74, 188, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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