Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad8a8cf88ab9d097221dd2a7a30b33625ac9de50fff34e329986b205d972f76

Tx prefix hash: 439f96ff8d721d3e2de6d92c69f1aeb0744f99c60d30784117600818225f29f9
Tx public key: 1aaf4329cd9957ce6a6de971bfcfeb2e5c15b049c39b52b06e3703ca62053753
Timestamp: 1736858440 Timestamp [UCT]: 2025-01-14 12:40:40 Age [y:d:h:m:s]: 00:155:11:02:09
Block: 1197177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110797 RingCT/type: yes/0
Extra: 011aaf4329cd9957ce6a6de971bfcfeb2e5c15b049c39b52b06e3703ca620537530211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 069e7c40cfc8b0ac8e260e08cd8879fd4423a5e041c5aa404a30c69dd4252bbf 0.600000000000 1683784 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": 1197187, "vin": [ { "gen": { "height": 1197177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "069e7c40cfc8b0ac8e260e08cd8879fd4423a5e041c5aa404a30c69dd4252bbf" } } ], "extra": [ 1, 26, 175, 67, 41, 205, 153, 87, 206, 106, 109, 233, 113, 191, 207, 235, 46, 92, 21, 176, 73, 195, 155, 82, 176, 110, 55, 3, 202, 98, 5, 55, 83, 2, 17, 0, 0, 0, 1, 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