Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37ce8868c7f4f3961f35fdd35f83cff6be49be906542d50e962d5abddc74936

Tx prefix hash: d768bb5a90ce874e455db8453635c1b725ff49b517aa62c856dcfc9015487ec3
Tx public key: c70811b644c982bbc945d1c7017be3c86b816e45a1cc0933309334a45fbda30d
Timestamp: 1734969919 Timestamp [UCT]: 2024-12-23 16:05:19 Age [y:d:h:m:s]: 00:091:19:07:23
Block: 1181578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65356 RingCT/type: yes/0
Extra: 01c70811b644c982bbc945d1c7017be3c86b816e45a1cc0933309334a45fbda30d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78af50d93f602df10e4ca4ff8080a258d5c03cb60d08a73d9b06fd7c4ff92dfe 0.600000000000 1668003 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": 1181588, "vin": [ { "gen": { "height": 1181578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78af50d93f602df10e4ca4ff8080a258d5c03cb60d08a73d9b06fd7c4ff92dfe" } } ], "extra": [ 1, 199, 8, 17, 182, 68, 201, 130, 187, 201, 69, 209, 199, 1, 123, 227, 200, 107, 129, 110, 69, 161, 204, 9, 51, 48, 147, 52, 164, 95, 189, 163, 13, 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