Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e8c8a057a71a98a7d8b9f62274e267ab5e1876fdbd831a100679a9e058edaa1

Tx prefix hash: d8c7a2eb009c4677695b3773c9f38a9a040ff2cfbeec4c65f2e693fc1fbe31ca
Tx public key: 80aaf8c11bed8e932b4ff5b2a69fdcf81b08c10a8e6d86f4b0fd1e3c74a82140
Timestamp: 1573462134 Timestamp [UCT]: 2019-11-11 08:48:54 Age [y:d:h:m:s]: 05:007:09:03:00
Block: 5434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1149677 RingCT/type: yes/0
Extra: 0180aaf8c11bed8e932b4ff5b2a69fdcf81b08c10a8e6d86f4b0fd1e3c74a82140

1 output(s) for total of 588.837961316000 dcy

stealth address amount amount idx
00: 356e29dd51541dc7acb33fd532bcad2071e9a7462dc371b04fe604f6a5c50c4c 588.837961316000 6058 of 0

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": 5444, "vin": [ { "gen": { "height": 5434 } } ], "vout": [ { "amount": 588837961316, "target": { "key": "356e29dd51541dc7acb33fd532bcad2071e9a7462dc371b04fe604f6a5c50c4c" } } ], "extra": [ 1, 128, 170, 248, 193, 27, 237, 142, 147, 43, 79, 245, 178, 166, 159, 220, 248, 27, 8, 193, 10, 142, 109, 134, 244, 176, 253, 30, 60, 116, 168, 33, 64 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8