Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e8b13cedba45fec1808cd8f36d5cbeb8d6e307e880955eacef775f78a8ce682

Tx prefix hash: 746f0daf8ff4dbbc0d6df761c8b45337c4942e6348a0c65a7030720a98b10dd4
Tx public key: b30a76f398038b469d84f7f5b70604ce616c72abb67ebae8895c3e204c7a7c55
Timestamp: 1725813934 Timestamp [UCT]: 2024-09-08 16:45:34 Age [y:d:h:m:s]: 00:105:01:24:26
Block: 1105760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75160 RingCT/type: yes/0
Extra: 01b30a76f398038b469d84f7f5b70604ce616c72abb67ebae8895c3e204c7a7c55021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54b5fa7d3a1545a6d30ba8edd784bef19bdaf1712e9255231580a5a4b037026 0.600000000000 1583209 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": 1105770, "vin": [ { "gen": { "height": 1105760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54b5fa7d3a1545a6d30ba8edd784bef19bdaf1712e9255231580a5a4b037026" } } ], "extra": [ 1, 179, 10, 118, 243, 152, 3, 139, 70, 157, 132, 247, 245, 183, 6, 4, 206, 97, 108, 114, 171, 182, 126, 186, 232, 137, 92, 62, 32, 76, 122, 124, 85, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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