Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18030a0794653f957fcd9d5baeefea7d7e66029b07a9296c460255274bd8da50

Tx prefix hash: 88e43c2d861de44b4c5afee673a42dc9cff0ef466cd5fef394f32fc8455f4be8
Tx public key: f0849268b59eeaee1412b3efc74f72aaacb4d2fa55b804b0b183a2861982672a
Timestamp: 1720147890 Timestamp [UCT]: 2024-07-05 02:51:30 Age [y:d:h:m:s]: 00:171:04:01:30
Block: 1058776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122522 RingCT/type: yes/0
Extra: 01f0849268b59eeaee1412b3efc74f72aaacb4d2fa55b804b0b183a2861982672a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304ff9b16fe76a753d4ccd53edc1e6aabea40d186a700325ca987585318bdbc9 0.600000000000 1529233 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": 1058786, "vin": [ { "gen": { "height": 1058776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304ff9b16fe76a753d4ccd53edc1e6aabea40d186a700325ca987585318bdbc9" } } ], "extra": [ 1, 240, 132, 146, 104, 181, 158, 234, 238, 20, 18, 179, 239, 199, 79, 114, 170, 172, 180, 210, 250, 85, 184, 4, 176, 177, 131, 162, 134, 25, 130, 103, 42, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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