Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a358c4c42cd65bacb3a528803444eab320715ee7a056b54ba688b4e50336ec37

Tx prefix hash: 8dff9b32baeb9fe1143c8d70e036887cc209ca55a1dd8cecbf4c76e38ee726e9
Tx public key: 1e9fbede646e7895259ceb7b206e1bb43ea5709d31a9da338d69885696bae184
Timestamp: 1729524510 Timestamp [UCT]: 2024-10-21 15:28:30 Age [y:d:h:m:s]: 00:229:16:33:27
Block: 1136481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164015 RingCT/type: yes/0
Extra: 011e9fbede646e7895259ceb7b206e1bb43ea5709d31a9da338d69885696bae1840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 948c5d4d04a1d90a2e4630cfc1344bf89f0aff39e5ac2878ea91a0b60e953cc6 0.600000000000 1619826 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": 1136491, "vin": [ { "gen": { "height": 1136481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "948c5d4d04a1d90a2e4630cfc1344bf89f0aff39e5ac2878ea91a0b60e953cc6" } } ], "extra": [ 1, 30, 159, 190, 222, 100, 110, 120, 149, 37, 156, 235, 123, 32, 110, 27, 180, 62, 165, 112, 157, 49, 169, 218, 51, 141, 105, 136, 86, 150, 186, 225, 132, 2, 17, 0, 0, 0, 2, 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