Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03c14064261fd6b97cb34da999544507ba34061cce8391ab5cfa2b361edb962

Tx prefix hash: 656ee474249c776de2d9d5a48fc94f663c45d5c2739f8316704b876aa745270b
Tx public key: 96d1e980f2f3b8b55254ec3c2f2e010239542da1f4cd3eb4d1bdf2a033fb3606
Timestamp: 1723592343 Timestamp [UCT]: 2024-08-13 23:39:03 Age [y:d:h:m:s]: 00:239:06:32:35
Block: 1087332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170896 RingCT/type: yes/0
Extra: 0196d1e980f2f3b8b55254ec3c2f2e010239542da1f4cd3eb4d1bdf2a033fb3606021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aacddb31b8ab7e82734277b790ca4afcab7965d3dda0bb7aad00bdfe15aead3 0.600000000000 1561939 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": 1087342, "vin": [ { "gen": { "height": 1087332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aacddb31b8ab7e82734277b790ca4afcab7965d3dda0bb7aad00bdfe15aead3" } } ], "extra": [ 1, 150, 209, 233, 128, 242, 243, 184, 181, 82, 84, 236, 60, 47, 46, 1, 2, 57, 84, 45, 161, 244, 205, 62, 180, 209, 189, 242, 160, 51, 251, 54, 6, 2, 17, 0, 0, 0, 5, 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